Scrapling Official Mcp Server

Created By
Karim Shoair9 months ago
The Scrapling MCP Server is a new feature that brings Scrapling's powerful Web Scraping capabilities directly to your favorite AI chatbot or AI agent. This integration allows you to scrape websites, extract data, and bypass anti-bot protections conversationally through Claude's AI interface or any other chatbot that supports MCP.
Overview

What is Scrapling Official MCP Server?

The Scrapling MCP Server is a feature that integrates Scrapling's web scraping capabilities with AI chatbots, allowing users to scrape websites, extract data, and bypass anti-bot protections conversationally.

How to use Scrapling MCP Server?

To use the Scrapling MCP Server, install Scrapling with MCP support and configure it with your AI chatbot, such as Claude. You can then issue commands to scrape data from websites directly through the chatbot interface.

Key features of Scrapling MCP Server?

  • Basic and dynamic content scraping tools.
  • Stealth scraping to bypass anti-bot systems.
  • Smart content extraction with CSS selector support.
  • Proxy support for anonymity and geo-targeting.
  • Parallel processing for efficient scraping.

Use cases of Scrapling MCP Server?

  1. Extracting product information from e-commerce sites.
  2. Scraping data from dynamic websites with JavaScript.
  3. Bypassing Cloudflare protections to access restricted content.

FAQ from Scrapling MCP Server?

  • Can I scrape any website?

You should check the website's robots.txt and comply with its terms of service.

  • Is it legal to scrape data?

Scraping must be done ethically, respecting copyright and privacy laws.

  • How do I handle anti-bot protections?

Use the stealth scraping tools provided by Scrapling to bypass these protections.

Server Config

{
  "mcpServers": {
    "ScraplingServer": {
      "command": "/Path/to/scrapling",
      "args": [
        "mcp"
      ]
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Karim Shoair
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago